docs: document private ingress with DNS-01 certificates#336
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: document private ingress with DNS-01 certificates#336mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new Security and Compliance page that documents the additional private ingress feature shipped in the upstream
feat: additional ingress DNS-01 cluster issuerPR.Context
The upstream change adds support for attaching an additional internal/private NLB to a Porter EKS cluster alongside the default public load balancer. Because the private ingress is unreachable from the public internet, certificate issuance switches from the HTTP-01 challenge to the ACME DNS-01 challenge, with cert-manager solving challenges via Cloudflare (API token secret) or Route 53 (cert-manager EKS Pod Identity, scoped to a single hosted zone).
Changes
security-and-compliance/private-ingress.mdxcovering what the private ingress is, when to use it, requirements, how to enable it, supported DNS providers (Cloudflare and Route 53), how to attach a service via thenginx-privateingress class, and troubleshooting.mint.jsonunder the Security and Compliance group, next to the existing Cloudflare DNS guide.cc @araujomauricio for review as the author of the triggering PR.